Autogenerated HTML docs for v1.8.1.2-545-g2f19ad
diff --git a/git-clone.html b/git-clone.html index 1446e95..205c5f9 100644 --- a/git-clone.html +++ b/git-clone.html
@@ -789,7 +789,7 @@ <dd> <p> When the repository to clone from is on a local machine, - this flag bypasses the normal "git aware" transport + this flag bypasses the normal "Git aware" transport mechanism and clones the repository by making a copy of HEAD and everything under objects and refs directories. The files under <code>.git/objects/</code> directory are hardlinked @@ -800,10 +800,10 @@ repository is specified as a URL, then this flag is ignored (and we never use the local optimizations). Specifying <code>--no-local</code> will override the default when <code>/path/to/repo</code> is given, using the regular -git transport instead.</p></div> +Git transport instead.</p></div> <div class="paragraph"><p>To force copying instead of hardlinking (which may be desirable if you are trying to make a back-up of your repository), but still avoid the -usual "git aware" transport mechanism, <code>--no-hardlinks</code> can be used.</p></div> +usual "Git aware" transport mechanism, <code>--no-hardlinks</code> can be used.</p></div> </dd> <dt class="hdlist1"> --no-hardlinks @@ -832,9 +832,9 @@ <div class="paragraph"><p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use it unless you understand what it does. If you clone your repository using this option and then delete branches (or use any -other git command that makes any existing commit unreferenced) in the +other Git command that makes any existing commit unreferenced) in the source repository, some objects may become unreferenced (or dangling). -These objects may be removed by normal git operations (such as <code>git commit</code>) +These objects may be removed by normal Git operations (such as <code>git commit</code>) which automatically call <code>git gc --auto</code>. (See <a href="git-gc.html">git-gc(1)</a>.) If these objects are removed and were referenced by the cloned repository, then the cloned repository will become corrupt.</p></div> @@ -913,7 +913,7 @@ </dt> <dd> <p> - Make a <em>bare</em> GIT repository. That is, instead of + Make a <em>bare</em> Git repository. That is, instead of creating <code><directory></code> and placing the administrative files in <code><directory>/.git</code>, make the <code><directory></code> itself the <code>$GIT_DIR</code>. This obviously implies the <code>-n</code> @@ -1061,8 +1061,8 @@ <p> Instead of placing the cloned repository where it is supposed to be, place the cloned repository at the specified directory, - then make a filesytem-agnostic git symbolic link to there. - The result is git repository can be separated from working + then make a filesytem-agnostic Git symbolic link to there. + The result is Git repository can be separated from working tree. </p> </dd> @@ -1156,7 +1156,7 @@ </p> </li> </ul></div> -<div class="paragraph"><p>For local repositories, also supported by git natively, the following +<div class="paragraph"><p>For local repositories, also supported by Git natively, the following syntaxes may be used:</p></div> <div class="ulist"><ul> <li> @@ -1172,7 +1172,7 @@ </ul></div> <div class="paragraph"><p>These two syntaxes are mostly equivalent, except the former implies --local option.</p></div> -<div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it +<div class="paragraph"><p>When Git doesn’t know how to handle a certain transport protocol, it attempts to use the <em>remote-<transport></em> remote helper, if one exists. To explicitly request a remote helper, the following syntax may be used:</p></div> @@ -1292,7 +1292,7 @@ <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated 2012-11-13 14:31:09 PST +Last updated 2013-02-05 21:07:26 PST </div> </div> </body>
